fix(todo-continuation-enforcer): use current selected model when continuing todos #151
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…inuing todos (#138) - Prioritize messages with model info when finding nearest message for todo continuation - Pass resolved model to session.prompt call to use previously selected model - Add comprehensive test cases for findNearestMessageWithFields logic 🤖 Generated with assistance of oh-my-opencode
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
todo-continuation-enforcershould use current selected model #138:todo-continuation-enforcernow uses the current selected model instead of defaulting to OpusChanges
findNearestMessageWithFieldsto prioritize messages with complete model info (providerID+modelID)modelpassthrough tosession.promptcall intodo-continuation-enforcerfindNearestMessageWithFieldsTesting
🤖 GENERATED WITH ASSISTANCE OF OhMyOpenCode